Port detection previously read the bare PORT or any *_PORT env var from pm2_env, which inside Conductor latched onto the inherited CONDUCTOR_PORT allocation — overriding an app's real port and giving non-server processes a phantom one. This replaces the heuristic with SocketScanner, which resolves each process's ports from the actual listening sockets (one lsof + one ps per refresh, machine-wide) and attributes ports opened by child processes too, so npm-wrapped servers (pm2 start npm -- run dev) resolve correctly. PM2Process.port (Int?) becomes ports ([Int]): the row shows up to two ports as links with a +N overflow badge and a tooltip listing all, while the env header keeps its band/range aggregated over the real ports. The decoder no longer enumerates pm2_env at all, IPv4/IPv6 bindings collapse, and debug/inspector ports (9229–9231) are filtered. Adds a pure PortDisplay helper and tests covering socket parsing, process-tree resolution, debug filtering, and the display logic.

🤖 Generated with Claude Code

Summary by cubic

Resolve PM2 ports from actual listening sockets instead of env vars to prevent phantom ports and correctly attribute child process listeners; the UI now shows up to two ports with a +N overflow and the env header aggregates real port ranges.

• Bug Fixes

  • Stop reading PORT/*_PORT from pm2_env; use SocketScanner (one lsof + one ps per refresh) to map ports by pid and descendants. Fixes CONDUCTOR_PORT bleed-through and npm-wrapped servers.
  • Collapse IPv4/IPv6 duplicates and filter debug ports 9229–9231.

• Refactors

  • Replace PM2Process.port with ports: [Int]; update search, env header band/range, and rows via ProcessPortsView (shows up to two ports with a +N tooltip).
  • Add pure PortDisplay helper and tests for socket parsing, process-tree resolution, debug filtering, and display logic; decoder no longer enumerates pm2_env.

^{Written for commit 74a8373. Summary will update on new commits.}